Required for #1997.

Adds support for passing the device_address flag when allocating DeviceMemory, which is required when binding memory to a buffer with the shader_device_address usage in the VK_KHR_buffer_device_address extension (and core 1.2 which it was promoted to), but not its predecessor VK_EXT_buffer_device_address. Fixes the bug where UnsafeBuffer::bind_memory wasn't validating if the memory is allocated with the device_address flag, and also fixes the wrong function pointer in BufferAccess::raw_device_address when not using the outdated VK_EXT_buffer_device_address extension.

Changelog:

### Breaking changes
Changes to buffers:
- When binding memory to a buffer with the `shader_device_address` usage, the memory must now have been allocated with the `MemoryAllocateFlags::device_address` flag set.

### Additions
- Added `MemoryAllocateFlags`.

### Bugs fixed
- Fixed missing validation when binding memory to a buffer with the `shader_device_address` usage.